home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The CDPD Public Domain Collection for CDTV 4
/
CDPD_IV.bin
/
e
/
mailinglists
/
amigae.0793july.archive
/
000070_crash!axion.bt.…uk!D.Higginson_Mon, 26 Jul 93 03:45:32 PST.msg
< prev
next >
Wrap
Internet Message Format
|
1994-05-26
|
1KB
Received: by bkhouse.cts.com (V1.16/Amiga)
id AA00000; Mon, 26 Jul 93 03:45:32 PST
Received: from zaphod.axion.bt.co.uk by crash.cts.com with smtp
(Smail3.1.28.1 #15) id m0oKPdS-0000moC; Mon, 26 Jul 93 03:18 PDT
Received: from elephant.axion.bt.co.uk by zaphod.axion.bt.co.uk with SMTP (PP); Mon, 26 Jul 1993 11:18:10 +0100
Message-Id: <m0oKPdS-0000moC@crash.cts.com>
Date: Mon, 26 Jul 93 11:18:08 BST
From: D.Higginson@axion.bt.co.uk
To: amigae@bkhouse.cts.com
Cc: D.Higginson@axion.bt.co.uk
Subject: Re: CHIP specifier
I would also greatly appreciate a chip specifier. What are
the advantages of storing this sort of data in a separate
file? IMO, it only creates problems for the end-user when
they come to copy your product to their hard disk or
whatever.
Why not give the compiler a command-line option to
incorporate graphics/sound files into the finished
program. E could give the program a pointer to a
structure which tells it where the memory is etc. In this
way, Amiga E could achieve a 'memory bank' type operation
which is what has helped AMOS become so incredibly
popular. What do you think Wouter? Is this feasible?
Other comments appreciated,
Dave.
P.S. I would love some feedback on my HAM posting i.e. was
it useful, and was it at the right level?